Discover gists

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

云

IaaS指提供系统（可以自己选）或者储存空间之类的硬件，软件要自己手动装；PaaS提供语言环境和框架（可以自己选）；SaaS只能使用开发好的软件（卖软件本身）；BaaS一般类似于非关系数据库，但各家不通用，有时还有一些其它东西。

其他人的集合

https://education.github.com/pack GitHub学生包，需用教育邮箱验证。各种福利，可从DigitalOcean上手
https://github.com/ripienaar/free-for-dev 本文尽量不与此项目重复
https://free.zhelper.net/
https://github.com/AchoArnold/discount-for-student-dev

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

	// Version 0.0.1
	module.exports = askChatWithPrompt;

	function askChat(str, app) {
	const prompt = encodeURI(str);

	const chatViewEl = app.workspace.getLeavesOfType("surfing-view").find((item)=>{ return /chat\.openai\.com/.test(item?.view?.currentUrl)}).view.webviewEl;
	chatViewEl.executeJavaScript(`
	var htmlElement = document.querySelector("textarea");
	htmlElement.value = decodeURI("${ prompt }");

	version: '3'
	services:
	n8n:
	image: docker.n8n.io/n8nio/n8n
	ports:
	- 5678:5678
	environment:
	- GENERIC_TIMEZONE=America/Chicago
	- TZ=America/Chicago

	# 1. First of all of course get Manjaro:
	https://manjaro.org/get-manjaro/

	# I recommend using Etcher to copy the image to your USB:
	https://etcher.io/

	# 2. Before installing make sure:
	# - Secure boot is disabled in BIOS
	# - Your SSD, HDD or NVME drive is set to AHCI instead of RAID
	# - Fastboot should be on Auto or minimal, but this shouldn't matter to much

	# Useful for testing things that are time zone
	# sensitive - like scheduling things

	# Get current timezone
	sudo systemsetup -gettimezone

	# Get list of available timezones
	sudo systemsetup -listtimezones

	# Set the timezone to the selected timezone

	git branch -m old_branch new_branch # Rename branch locally
	git push origin :old_branch # Delete the old branch
	git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote

	{
	"data": "%data%"
	}